\documentclass{acm_proc_article-sp}
\usepackage{algorithm}
\usepackage{algorithmic}

\usepackage{epsfig}
\usepackage{url}
\begin{document}

\title{An Implementation of Two Phase Locking (2PL) and Optimistic Concurrency Control(OCC) on Google App Engine}
\numberofauthors{2} 
\author{
\alignauthor
Puneet Lakhina\\
       \affaddr{University of California, Santa Barbara}\\
       \email{puneet@cs.ucsb.edu}
% 2nd. author
\alignauthor
Neer Shay\\
       \affaddr{University of California, Santa Barbara}\\
       \email{neershay@umail.ucsb.edu}
}
\maketitle
\begin{abstract}
Concurrency Control in Databases is implemented mainly through two strategies, locking or optimistic concurrency control. Through the means of this paper we compare the implementations of these two strategies and provide a comparative analysis on the relative performance of the two. The vehicle for this analysis is a transactional datastore built using the Google App Engine which utilizes Google Datastore API. We have implemented the Strong Strict Two Phase Locking (SS2PL) version of locking and Parallel Validation version of the Optimistic Concurrency Control. In addition to a study of the two concurrency control protocols, we also highlight the nuances of their implementation using Google App Engine and on using the "New Age" key-value App Engine Datasotre API as our backend storage.
\end{abstract}

% A category with the (minimum) three required fields
\category{H.4}{Database Management Systems}{Systems - Concurrency, Transaction Processing}

\keywords{Optimistic Concurrency Control, Two Phase Locking, Google App Engine, Datastore}

\input{introduction}
\input{implementation}
\input{performancetesting}
\input{futurework}
\input{conclusion}
\bibliographystyle{abbrv}
\bibliography{references}
\end{document}
